Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad63ed18ffda0df3186e56034bb5f7e1c66ea0c04582fb93e6b8f584ab05c4d6

Tx prefix hash: 1585b27643491fc96723b00ad717ce28d244113580f295ace644ef3d9166f327
Tx public key: 8ffc39be5a6fc953c29c441e18b1f5caba59359b1d95a2656f67f6708a295c63
Timestamp: 1672865693 Timestamp [UCT]: 2023-01-04 20:54:53 Age [y:d:h:m:s]: 01:315:07:35:11
Block: 667657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486343 RingCT/type: yes/0
Extra: 018ffc39be5a6fc953c29c441e18b1f5caba59359b1d95a2656f67f6708a295c6302110000000875e3f0e9000000000000000000

1 output(s) for total of 3.765088267000 dcy

stealth address amount amount idx
00: 5c6c654e5d6e7d1af3be458630d345db6e181a3719cb5e15b1e1367e09b1e893 3.765088267000 1108872 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": 667667, "vin": [ { "gen": { "height": 667657 } } ], "vout": [ { "amount": 3765088267, "target": { "key": "5c6c654e5d6e7d1af3be458630d345db6e181a3719cb5e15b1e1367e09b1e893" } } ], "extra": [ 1, 143, 252, 57, 190, 90, 111, 201, 83, 194, 156, 68, 30, 24, 177, 245, 202, 186, 89, 53, 155, 29, 149, 162, 101, 111, 103, 246, 112, 138, 41, 92, 99, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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