Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c4c9fa9d7afad725e7536e7fd04bcefbb1d7217f20c334ca844757047ada31b

Tx prefix hash: 5927776473aee7d7d70ae53cb0319b1410198bb99f0e8594cdf10c91d3bc1df1
Tx public key: 0736e968ca620781da6d0a0897c180b0d4a1e237161474b640fbe2cedc5120df
Timestamp: 1681255188 Timestamp [UCT]: 2023-04-11 23:19:48 Age [y:d:h:m:s]: 01:295:16:18:10
Block: 736571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472593 RingCT/type: yes/0
Extra: 010736e968ca620781da6d0a0897c180b0d4a1e237161474b640fbe2cedc5120df0211000000015029cbac000000000000000000

1 output(s) for total of 2.225536568000 dcy

stealth address amount amount idx
00: dbceefe1aef89f9f07b9e03345af1fd8baae79f5501e3f73e2f0f4922115eff1 2.225536568000 1183022 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": 736581, "vin": [ { "gen": { "height": 736571 } } ], "vout": [ { "amount": 2225536568, "target": { "key": "dbceefe1aef89f9f07b9e03345af1fd8baae79f5501e3f73e2f0f4922115eff1" } } ], "extra": [ 1, 7, 54, 233, 104, 202, 98, 7, 129, 218, 109, 10, 8, 151, 193, 128, 176, 212, 161, 226, 55, 22, 20, 116, 182, 64, 251, 226, 206, 220, 81, 32, 223, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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