Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9da07bd0a164d9dec3e48ec9b920ae79e0d964e81172845c9da729f56c442fb

Tx prefix hash: 599f02208fcbabf1856884536273f55a28f052f591dd0331391da9bb7a4e3340
Tx public key: b899d46bf85407ba24d42df752cb36536141c5aeef51c9f5a0330d4a4bdc1762
Timestamp: 1728078202 Timestamp [UCT]: 2024-10-04 21:43:22 Age [y:d:h:m:s]: 00:174:16:09:37
Block: 1124529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124629 RingCT/type: yes/0
Extra: 01b899d46bf85407ba24d42df752cb36536141c5aeef51c9f5a0330d4a4bdc176202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50963b66a11f336c1832c4e170bd319385e42fd6c2aa23817afd8e7b0c4cbd1e 0.600000000000 1607166 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": 1124539, "vin": [ { "gen": { "height": 1124529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50963b66a11f336c1832c4e170bd319385e42fd6c2aa23817afd8e7b0c4cbd1e" } } ], "extra": [ 1, 184, 153, 212, 107, 248, 84, 7, 186, 36, 212, 45, 247, 82, 203, 54, 83, 97, 65, 197, 174, 239, 81, 201, 245, 160, 51, 13, 74, 75, 220, 23, 98, 2, 17, 0, 0, 0, 4, 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