Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d1245d06c291c835185738c72ebb0da0a6aa1d5f7b658cbf0e404b66c57cab

Tx prefix hash: c9fb8c230f369e73e69786a6496c6d7ffe7a18ffa5655ad06b6919e5051f6e1d
Tx public key: 0c994a41e559f83587ac4b3baea771944d2eef203a98e1e79b7070f3c4143151
Timestamp: 1738483509 Timestamp [UTC]: 2025-02-02 08:05:09 Age [y:d:h:m:s]: 01:214:10:41:54
Block: 1210365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417826 RingCT/type: yes/0
Extra: 010c994a41e559f83587ac4b3baea771944d2eef203a98e1e79b7070f3c41431510211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52b2a50c4118c575f5dd14739553e2acf6d0d8040aeec49c3321aac837783e73 0.000600000000 1697116 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": 1210375, "vin": [ { "gen": { "height": 1210365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b2a50c4118c575f5dd14739553e2acf6d0d8040aeec49c3321aac837783e73" } } ], "extra": [ 1, 12, 153, 74, 65, 229, 89, 248, 53, 135, 172, 75, 59, 174, 167, 113, 148, 77, 46, 239, 32, 58, 152, 225, 231, 155, 112, 112, 243, 196, 20, 49, 81, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: