Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a8f615d3370ead150590ba7f86c06acebfb867cf103f0c1412c3b293fb7e9cbb

Tx prefix hash: fc6f659a28352b5b85f40565cdc78735b2cbda4a18c19fff99f5aba8ab107604
Tx public key: d438789e5eb2f251a77de122f5100b6d3369bd5e033670844f7fae9afbbf83e8
Timestamp: 1772837022 Timestamp [UTC]: 2026-03-06 22:43:42 Age [y:d:h:m:s]: 00:257:21:03:41
Block: 1492240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189874 RingCT/type: yes/0
Extra: 01d438789e5eb2f251a77de122f5100b6d3369bd5e033670844f7fae9afbbf83e8021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f66d4ef468ab241dcabc97689eb2e1f7a19bd5261d5ff6611d01f1069df32c9d 0.000600000000 1981780 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1492250, "vin": [ { "gen": { "height": 1492240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f66d4ef468ab241dcabc97689eb2e1f7a19bd5261d5ff6611d01f1069df32c9d" } } ], "extra": [ 1, 212, 56, 120, 158, 94, 178, 242, 81, 167, 125, 225, 34, 245, 16, 11, 109, 51, 105, 189, 94, 3, 54, 112, 132, 79, 127, 174, 154, 251, 191, 131, 232, 2, 17, 0, 0, 0, 8, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: