Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 822f77907c9ec63924ed4e8b140183071aef02900eee54151d6d776dcfc983ab

Tx prefix hash: 146c83e427e537d46792a44cd692c5f510eb9504d8252bd7df8ca4b066a20339
Tx public key: a23eef5df74acf97b0df791c3930050750d53a6b3d3e899a4d9128f98041d46f
Timestamp: 1733511550 Timestamp [UCT]: 2024-12-06 18:59:10 Age [y:d:h:m:s]: 00:111:19:30:47
Block: 1169468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79709 RingCT/type: yes/0
Extra: 01a23eef5df74acf97b0df791c3930050750d53a6b3d3e899a4d9128f98041d46f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0f46649ef51fef96d9689e24cbf688f3a93a9903a3f87c7a8da5219b2810e4 0.600000000000 1655187 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": 1169478, "vin": [ { "gen": { "height": 1169468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0f46649ef51fef96d9689e24cbf688f3a93a9903a3f87c7a8da5219b2810e4" } } ], "extra": [ 1, 162, 62, 239, 93, 247, 74, 207, 151, 176, 223, 121, 28, 57, 48, 5, 7, 80, 213, 58, 107, 61, 62, 137, 154, 77, 145, 40, 249, 128, 65, 212, 111, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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