Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c9d85c890aac4c95c4bb68c707a8cc23aeb2a550309a46493321ff9225e49a

Tx prefix hash: d408a0db74fd7f7d6ba5d3ee7a609d102aa1396d0212b17ed9ab04ae479631b6
Tx public key: 7c1a34cb738de735cb8dd7591deb20a48d21c204bd8b4cf65e0e37dc312961d6
Timestamp: 1725475510 Timestamp [UCT]: 2024-09-04 18:45:10 Age [y:d:h:m:s]: 00:263:05:12:26
Block: 1102945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188017 RingCT/type: yes/0
Extra: 017c1a34cb738de735cb8dd7591deb20a48d21c204bd8b4cf65e0e37dc312961d602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d274cef1053006928f022f1597c0889779d07080d5a03f89f072e2de4921b1e 0.600000000000 1579586 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 dinasty-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": 1102955, "vin": [ { "gen": { "height": 1102945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d274cef1053006928f022f1597c0889779d07080d5a03f89f072e2de4921b1e" } } ], "extra": [ 1, 124, 26, 52, 203, 115, 141, 231, 53, 203, 141, 215, 89, 29, 235, 32, 164, 141, 33, 194, 4, 189, 139, 76, 246, 94, 14, 55, 220, 49, 41, 97, 214, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8