Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4436aabda1695eb24589dc9a32dd8fc254fefdf70d6c8c83c40844738dbb83c

Tx prefix hash: c7917122876487f0e8dcd72e1afeab2b83574f2e75c1272431a4c48c513ee72d
Tx public key: 28df08e57c272f285b617bbeefa0fc4360c4a805c2c99166eee33821c1eaf88b
Timestamp: 1709995330 Timestamp [UCT]: 2024-03-09 14:42:10 Age [y:d:h:m:s]: 01:253:12:19:35
Block: 974617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439909 RingCT/type: yes/0
Extra: 0128df08e57c272f285b617bbeefa0fc4360c4a805c2c99166eee33821c1eaf88b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d61054b1b95b567282d30f5b895eb6b9eb2e531c43bf0ccb00a6fabda2847a2b 0.600000000000 1434576 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": 974627, "vin": [ { "gen": { "height": 974617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d61054b1b95b567282d30f5b895eb6b9eb2e531c43bf0ccb00a6fabda2847a2b" } } ], "extra": [ 1, 40, 223, 8, 229, 124, 39, 47, 40, 91, 97, 123, 190, 239, 160, 252, 67, 96, 196, 168, 5, 194, 201, 145, 102, 238, 227, 56, 33, 193, 234, 248, 139, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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