Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 141ac8925048c206b26f3e9d3ef0267472a47847cb191d65214000d3157f2ff1

Tx prefix hash: 63cea6880c01c5ac19da9a1a07e23f0de2cf4a7dfdc69534c39d23c39fa15185
Tx public key: edf35720268df8362e6fc06f572776ae941dfcfac759db37c5ae78f9f74672d4
Timestamp: 1660816288 Timestamp [UCT]: 2022-08-18 09:51:28 Age [y:d:h:m:s]: 02:229:12:48:20
Block: 568441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685260 RingCT/type: yes/0
Extra: 01edf35720268df8362e6fc06f572776ae941dfcfac759db37c5ae78f9f74672d402110000000275e3f0e9000000000000000000

1 output(s) for total of 8.026368617000 dcy

stealth address amount amount idx
00: 0ae3ed466f813e244e546cd56c8f8c09d9410eca5f5246bd61d2ebeef7d7931a 8.026368617000 1001568 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": 568451, "vin": [ { "gen": { "height": 568441 } } ], "vout": [ { "amount": 8026368617, "target": { "key": "0ae3ed466f813e244e546cd56c8f8c09d9410eca5f5246bd61d2ebeef7d7931a" } } ], "extra": [ 1, 237, 243, 87, 32, 38, 141, 248, 54, 46, 111, 192, 111, 87, 39, 118, 174, 148, 29, 252, 250, 199, 89, 219, 55, 197, 174, 120, 249, 247, 70, 114, 212, 2, 17, 0, 0, 0, 2, 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