Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5398e92881ac04cde122f90bb9ccf9d10214022abbc32ee12bdffa69d806351a

Tx prefix hash: a6fc27455f79c82e0bc0a153b6e3b91b2f42fdf1de2616bf86f813736fb06bf9
Tx public key: 8834eb41768fe7104eb3f19ec91d69dcf925576866a2c0aecfc4ea3f55fcdd08
Timestamp: 1577732341 Timestamp [UCT]: 2019-12-30 18:59:01 Age [y:d:h:m:s]: 05:000:00:56:22
Block: 35256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149970 RingCT/type: yes/0
Extra: 018834eb41768fe7104eb3f19ec91d69dcf925576866a2c0aecfc4ea3f55fcdd08021100000111c5b5978f000000000000000000

1 output(s) for total of 469.011067513000 dcy

stealth address amount amount idx
00: c735f502320e0dca3da10b46188f3a40d05a7e648cf9d848c8b83ba0f2f611b4 469.011067513000 59366 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": 35266, "vin": [ { "gen": { "height": 35256 } } ], "vout": [ { "amount": 469011067513, "target": { "key": "c735f502320e0dca3da10b46188f3a40d05a7e648cf9d848c8b83ba0f2f611b4" } } ], "extra": [ 1, 136, 52, 235, 65, 118, 143, 231, 16, 78, 179, 241, 158, 201, 29, 105, 220, 249, 37, 87, 104, 102, 162, 192, 174, 207, 196, 234, 63, 85, 252, 221, 8, 2, 17, 0, 0, 1, 17, 197, 181, 151, 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