Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15246446d3d094ed42206f54f66eb6c0cabbe746f1f9e03dbf1de2b83cbc1c7d

Tx prefix hash: bf1ec3c57e3a5092b2f27e59e28ac5a4913309c302b07dfdf3d11722e998b191
Tx public key: dc035af1c1abef5a40aa8da6a6f4382c19cbeaf188348c07f03b5718bada5d05
Timestamp: 1744953884 Timestamp [UTC]: 2025-04-18 05:24:44 Age [y:d:h:m:s]: 01:129:00:38:20
Block: 1263928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356559 RingCT/type: yes/0
Extra: 01dc035af1c1abef5a40aa8da6a6f4382c19cbeaf188348c07f03b5718bada5d050211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b70098dbb16e41e369fd3bc0f37cbf47235061bf138e1f3d44299b5323aeff9a 0.000600000000 1751121 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": 1263938, "vin": [ { "gen": { "height": 1263928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70098dbb16e41e369fd3bc0f37cbf47235061bf138e1f3d44299b5323aeff9a" } } ], "extra": [ 1, 220, 3, 90, 241, 193, 171, 239, 90, 64, 170, 141, 166, 166, 244, 56, 44, 25, 203, 234, 241, 136, 52, 140, 7, 240, 59, 87, 24, 186, 218, 93, 5, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: