Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1376611627d12a3df8b3c0dc62c369d1ed01a80fd216082eaca702a07511580f

Tx prefix hash: 712d18632b7436325aaca546fa1c38570b6dc7b55c839bf98008c21055cad9aa
Tx public key: 8a93fd6f13440e29db0d2efcf8b5edc0caf65a0afab99ffac9c395dd178277e0
Timestamp: 1583977054 Timestamp [UCT]: 2020-03-12 01:37:34 Age [y:d:h:m:s]: 05:245:17:07:40
Block: 80867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1329120 RingCT/type: yes/0
Extra: 018a93fd6f13440e29db0d2efcf8b5edc0caf65a0afab99ffac9c395dd178277e0021100000001640ff48f000000000000000000

1 output(s) for total of 331.172943540000 dcy

stealth address amount amount idx
00: 68908cb279d79d4fc98445a7b2976ef3e1ad5ec59146ce34686a2835396ae87f 331.172943540000 147933 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": 80877, "vin": [ { "gen": { "height": 80867 } } ], "vout": [ { "amount": 331172943540, "target": { "key": "68908cb279d79d4fc98445a7b2976ef3e1ad5ec59146ce34686a2835396ae87f" } } ], "extra": [ 1, 138, 147, 253, 111, 19, 68, 14, 41, 219, 13, 46, 252, 248, 181, 237, 192, 202, 246, 90, 10, 250, 185, 159, 250, 201, 195, 149, 221, 23, 130, 119, 224, 2, 17, 0, 0, 0, 1, 100, 15, 244, 143, 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