Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df8b3f188d7d48e102530080dd3d01e644bb7ee3265fb3d2376565d80337c57f

Tx prefix hash: d08ce7928e14b69bd8e809b80f5dbc40c206997ad5dec887e99e7e737b6b8e90
Tx public key: c9df2bc2061661b319a1b56ec5d1f26bbf38f85296c5615843d2074fb45c2154
Timestamp: 1721116059 Timestamp [UCT]: 2024-07-16 07:47:39 Age [y:d:h:m:s]: 01:139:10:08:55
Block: 1066822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358179 RingCT/type: yes/0
Extra: 01c9df2bc2061661b319a1b56ec5d1f26bbf38f85296c5615843d2074fb45c215402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be2b516ba0face1b554034c7bcc9ac1571cd4a78e775e31d5c35d9077abee40 0.600000000000 1537491 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": 1066832, "vin": [ { "gen": { "height": 1066822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be2b516ba0face1b554034c7bcc9ac1571cd4a78e775e31d5c35d9077abee40" } } ], "extra": [ 1, 201, 223, 43, 194, 6, 22, 97, 179, 25, 161, 181, 110, 197, 209, 242, 107, 191, 56, 248, 82, 150, 197, 97, 88, 67, 210, 7, 79, 180, 92, 33, 84, 2, 17, 0, 0, 0, 3, 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