Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 197a4fbfca1262d69a38acfa16393cac2c2cf7c50df0376e15384386a099d543

Tx prefix hash: 82501bf53f587df56bcf1f4a50df1650441c857a4adde6a522f53fda77976724
Tx public key: bd0215c0b8a14bd73bd897f46ca009e4dd7e054e97ad1220239603794e795a0a
Timestamp: 1698331746 Timestamp [UCT]: 2023-10-26 14:49:06 Age [y:d:h:m:s]: 01:197:09:16:23
Block: 878134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402083 RingCT/type: yes/0
Extra: 01bd0215c0b8a14bd73bd897f46ca009e4dd7e054e97ad1220239603794e795a0a0211000000034b8f5122000000000000000000

1 output(s) for total of 0.755748933000 dcy

stealth address amount amount idx
00: be15d4d51993d47a7171d198c571d0e7ea30b1a024e64ea0734d62b0128d8194 0.755748933000 1333548 of 0

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": 878144, "vin": [ { "gen": { "height": 878134 } } ], "vout": [ { "amount": 755748933, "target": { "key": "be15d4d51993d47a7171d198c571d0e7ea30b1a024e64ea0734d62b0128d8194" } } ], "extra": [ 1, 189, 2, 21, 192, 184, 161, 75, 215, 59, 216, 151, 244, 108, 160, 9, 228, 221, 126, 5, 78, 151, 173, 18, 32, 35, 150, 3, 121, 78, 121, 90, 10, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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