Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29e6634a659dcf94584bed7f4c9870611a1548764bae91916647a24fcd28c10e

Tx prefix hash: 0f0eb8dbcb77b2d2a713dffa3025762ffc0372fdbc7834bf34efe94fdd688aae
Tx public key: 5213dfe0163daa4227a2139c6b8d1995f94368c7c92cb418f920a7409c17836a
Timestamp: 1577741144 Timestamp [UCT]: 2019-12-30 21:25:44 Age [y:d:h:m:s]: 04:364:22:47:48
Block: 35334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149900 RingCT/type: yes/0
Extra: 015213dfe0163daa4227a2139c6b8d1995f94368c7c92cb418f920a7409c17836a0211000000054943cd9f000000000000000000

1 output(s) for total of 468.765994382000 dcy

stealth address amount amount idx
00: 83610858abd0a092a7e11ffee260da2cf876f77530e1b98fbd6aad3b897dcfad 468.765994382000 59518 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": 35344, "vin": [ { "gen": { "height": 35334 } } ], "vout": [ { "amount": 468765994382, "target": { "key": "83610858abd0a092a7e11ffee260da2cf876f77530e1b98fbd6aad3b897dcfad" } } ], "extra": [ 1, 82, 19, 223, 224, 22, 61, 170, 66, 39, 162, 19, 156, 107, 141, 25, 149, 249, 67, 104, 199, 201, 44, 180, 24, 249, 32, 167, 64, 156, 23, 131, 106, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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