Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7014651d4d1fc52d490496e5281c97fd9b9faf46b3e585685c1e4055330355fa

Tx prefix hash: 0ae2f73e947a72d24518714e170e528bcae9b0362adb68f369b4517cc05ea0cd
Tx public key: efc3f6aea63e0e859e13e4ce23104740665fa63c8f8f2ccefdf72daf3121f81e
Timestamp: 1636275742 Timestamp [UCT]: 2021-11-07 09:02:22 Age [y:d:h:m:s]: 03:127:14:25:45
Block: 369172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869563 RingCT/type: yes/0
Extra: 01efc3f6aea63e0e859e13e4ce23104740665fa63c8f8f2ccefdf72daf3121f81e0211000000016e80e2c6000000000000000000

1 output(s) for total of 36.709655501000 dcy

stealth address amount amount idx
00: a2d586cca6200e97a994ee0ffcc449591cce31ebd128fcd7cff994a51dd83812 36.709655501000 748636 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": 369182, "vin": [ { "gen": { "height": 369172 } } ], "vout": [ { "amount": 36709655501, "target": { "key": "a2d586cca6200e97a994ee0ffcc449591cce31ebd128fcd7cff994a51dd83812" } } ], "extra": [ 1, 239, 195, 246, 174, 166, 62, 14, 133, 158, 19, 228, 206, 35, 16, 71, 64, 102, 95, 166, 60, 143, 143, 44, 206, 253, 247, 45, 175, 49, 33, 248, 30, 2, 17, 0, 0, 0, 1, 110, 128, 226, 198, 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