Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11647dcd002af0565fa3c8111b6afb66ff570c12d8bc9629b60950c3da42daf5

Tx prefix hash: 2197db3a5ee5680902f6bc76baae508668a79832af70b462f4b46e6dcf710299
Tx public key: aab44ed2de8618a375a8459d60156b956f18be346820c33f716c6a1ac8f75efe
Timestamp: 1577902682 Timestamp [UCT]: 2020-01-01 18:18:02 Age [y:d:h:m:s]: 05:309:03:47:57
Block: 36508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1368557 RingCT/type: yes/0
Extra: 01aab44ed2de8618a375a8459d60156b956f18be346820c33f716c6a1ac8f75efe02110000002c4943cd9f000000000000000000

1 output(s) for total of 464.552384447000 dcy

stealth address amount amount idx
00: 5d81e7d3c14a2afa45ce9d56a98c824d635ee29e239e0d9b453d5fc0248ebd7a 464.552384447000 61866 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": 36518, "vin": [ { "gen": { "height": 36508 } } ], "vout": [ { "amount": 464552384447, "target": { "key": "5d81e7d3c14a2afa45ce9d56a98c824d635ee29e239e0d9b453d5fc0248ebd7a" } } ], "extra": [ 1, 170, 180, 78, 210, 222, 134, 24, 163, 117, 168, 69, 157, 96, 21, 107, 149, 111, 24, 190, 52, 104, 32, 195, 63, 113, 108, 106, 26, 200, 247, 94, 254, 2, 17, 0, 0, 0, 44, 73, 67, 205, 159, 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