Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee2f4d158fdb3e8fedb80e435f80d617b43063c0759cb6978bf7c222eb8e996

Tx prefix hash: 209fd50562d8c18580ba0b1d33461b57a84a6a029f45d115bc08454ae998bc94
Tx public key: 598f08a25d401f4e08123d056a659b9f7a133dff7680463f7153ef8149ba8a26
Timestamp: 1772920906 Timestamp [UTC]: 2026-03-07 22:01:46 Age [y:d:h:m:s]: 00:252:22:03:09
Block: 1492933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186197 RingCT/type: yes/0
Extra: 01598f08a25d401f4e08123d056a659b9f7a133dff7680463f7153ef8149ba8a26021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 70562842f4c24f9f4025e9d04e1de4f348beb9fbbcd44c88dc341304a2ddbfe4 0.000600000000 1982485 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": 1492943, "vin": [ { "gen": { "height": 1492933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70562842f4c24f9f4025e9d04e1de4f348beb9fbbcd44c88dc341304a2ddbfe4" } } ], "extra": [ 1, 89, 143, 8, 162, 93, 64, 31, 78, 8, 18, 61, 5, 106, 101, 155, 159, 122, 19, 61, 255, 118, 128, 70, 63, 113, 83, 239, 129, 73, 186, 138, 38, 2, 17, 0, 0, 0, 7, 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: