Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19bb01f049965ce0da9a2dcf70733cbf569c10d574a4c30e9e07926b55611ad7

Tx prefix hash: bca936e549d6949b1f0c545f6f6de645677b7fe40ac1bba69f4e058e835a9b47
Tx public key: 84d46a40e95af8160777a506e3a31549fc00d87482c90fb8861717010b47531d
Timestamp: 1579798264 Timestamp [UCT]: 2020-01-23 16:51:04 Age [y:d:h:m:s]: 05:041:00:59:45
Block: 51545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179847 RingCT/type: yes/0
Extra: 0184d46a40e95af8160777a506e3a31549fc00d87482c90fb8861717010b47531d02110000000617786bcf000000000000000000

1 output(s) for total of 414.200718936000 dcy

stealth address amount amount idx
00: 428ff6bb7244a68144e4eda412c8cdf393b34358f1e7150c0f337dc638f2b0cb 414.200718936000 95582 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": 51555, "vin": [ { "gen": { "height": 51545 } } ], "vout": [ { "amount": 414200718936, "target": { "key": "428ff6bb7244a68144e4eda412c8cdf393b34358f1e7150c0f337dc638f2b0cb" } } ], "extra": [ 1, 132, 212, 106, 64, 233, 90, 248, 22, 7, 119, 165, 6, 227, 163, 21, 73, 252, 0, 216, 116, 130, 201, 15, 184, 134, 23, 23, 1, 11, 71, 83, 29, 2, 17, 0, 0, 0, 6, 23, 120, 107, 207, 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