Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2895c7d4b53fcf7a093b86860f927d76211b718a7dea03809e5ff84f13a9464

Tx prefix hash: 2eaf1393e0f6b9cce67f1e736674f88212ea0ba765bf935ced61f8df27805cdc
Tx public key: 72979f2197ef33105baa17ad4c3a08bfa85942b0fd14f1fa58acac4e275ce1b9
Timestamp: 1698525825 Timestamp [UTC]: 2023-10-28 20:43:45 Age [y:d:h:m:s]: 03:025:12:06:55
Block: 879738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803756 RingCT/type: yes/0
Extra: 0172979f2197ef33105baa17ad4c3a08bfa85942b0fd14f1fa58acac4e275ce1b9021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.000746556743 xmr

stealth address amount amount idx tag
00: 2356a50d280a1a7d85c762217aec974994982a7db4b1796a8ef0799d66665d04 0.000746556743 1335274 of 0 -

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": 879748, "vin": [ { "gen": { "height": 879738 } } ], "vout": [ { "amount": 746556743, "target": { "key": "2356a50d280a1a7d85c762217aec974994982a7db4b1796a8ef0799d66665d04" } } ], "extra": [ 1, 114, 151, 159, 33, 151, 239, 51, 16, 91, 170, 23, 173, 76, 58, 8, 191, 168, 89, 66, 176, 253, 20, 241, 250, 88, 172, 172, 78, 39, 92, 225, 185, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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: