Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2281a608e1afcdd1599548ada7bae95832b7e025bfe9f83a499bb24e5b71eb7b

Tx prefix hash: 2ec5f10dd5e1615deb37007ac12215991e0a8d51efb860247f488e3c8848c4ff
Tx public key: edcb3d6639764b8e3ee28f311f958177679ff642e49fa53a42ecdfa4701cecd2
Timestamp: 1635291198 Timestamp [UCT]: 2021-10-26 23:33:18 Age [y:d:h:m:s]: 04:009:01:38:54
Block: 361177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043275 RingCT/type: yes/0
Extra: 01edcb3d6639764b8e3ee28f311f958177679ff642e49fa53a42ecdfa4701cecd20211000000014a0f5013000000000000000000

1 output(s) for total of 39.018545357000 dcy

stealth address amount amount idx
00: 10b2b9a9c6e77d5e7b75d14daae12d20bd78de565cbac2dbdea43654b2f6aa23 39.018545357000 734906 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": 361187, "vin": [ { "gen": { "height": 361177 } } ], "vout": [ { "amount": 39018545357, "target": { "key": "10b2b9a9c6e77d5e7b75d14daae12d20bd78de565cbac2dbdea43654b2f6aa23" } } ], "extra": [ 1, 237, 203, 61, 102, 57, 118, 75, 142, 62, 226, 143, 49, 31, 149, 129, 119, 103, 159, 246, 66, 228, 159, 165, 58, 66, 236, 223, 164, 112, 28, 236, 210, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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