Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ac3960d420e9758854d96b7afd6d7a62c4e91b3d84e8302f2d49f903e70453

Tx prefix hash: 5c5a9de89c4fb8129b8496f586eac18dc2e077be005853e336d00095aa4a7fde
Tx public key: 546ab7daa87dff0991d52b9f17a38d78b5d484241e0b1397fda407ae56994cc9
Timestamp: 1577030489 Timestamp [UCT]: 2019-12-22 16:01:29 Age [y:d:h:m:s]: 05:063:22:53:36
Block: 29674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195172 RingCT/type: yes/0
Extra: 01546ab7daa87dff0991d52b9f17a38d78b5d484241e0b1397fda407ae56994cc9021100000038d81c26c0000000000000000000

1 output(s) for total of 489.416472502000 dcy

stealth address amount amount idx
00: 8b0e5ebcdb7cdf62dd31f92a73ba74bfc4f6429a128f06906e92520d24681311 489.416472502000 48842 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": 29684, "vin": [ { "gen": { "height": 29674 } } ], "vout": [ { "amount": 489416472502, "target": { "key": "8b0e5ebcdb7cdf62dd31f92a73ba74bfc4f6429a128f06906e92520d24681311" } } ], "extra": [ 1, 84, 106, 183, 218, 168, 125, 255, 9, 145, 213, 43, 159, 23, 163, 141, 120, 181, 212, 132, 36, 30, 11, 19, 151, 253, 164, 7, 174, 86, 153, 76, 201, 2, 17, 0, 0, 0, 56, 216, 28, 38, 192, 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