Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ed314c689aac54f6fd63609723c26277c7a04b59710b2ba2078269822cf55d9

Tx prefix hash: 7b33cebe2a6e3def9b9c665e9445871e972bc1ae56ae0a39fb85b7695922a7be
Tx public key: 73936d798943ca1a3648121a0f5acad3570a8d67008089d6fc4178b5b43f3f74
Timestamp: 1636972464 Timestamp [UCT]: 2021-11-15 10:34:24 Age [y:d:h:m:s]: 03:116:20:30:57
Block: 374766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 862041 RingCT/type: yes/0
Extra: 0173936d798943ca1a3648121a0f5acad3570a8d67008089d6fc4178b5b43f3f74021100000012e9564d6f000000000000000000

1 output(s) for total of 35.176496924000 dcy

stealth address amount amount idx
00: c1b84b1e9dea25d6add6b61bb692c97e3b4d7f37759eb43b4daf05e10ac73325 35.176496924000 758488 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": 374776, "vin": [ { "gen": { "height": 374766 } } ], "vout": [ { "amount": 35176496924, "target": { "key": "c1b84b1e9dea25d6add6b61bb692c97e3b4d7f37759eb43b4daf05e10ac73325" } } ], "extra": [ 1, 115, 147, 109, 121, 137, 67, 202, 26, 54, 72, 18, 26, 15, 90, 202, 211, 87, 10, 141, 103, 0, 128, 137, 214, 252, 65, 120, 181, 180, 63, 63, 116, 2, 17, 0, 0, 0, 18, 233, 86, 77, 111, 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