Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de614733aa852c55bfe76cfb03527856aae1b5beaef8ef6178a47b625646158

Tx prefix hash: 7fa8ec0761d31916dc27fa971414c2a245889751c9a0d655691892676023fb65
Tx public key: 730510b6d2844966fa32393c28e03d8d23ab35e43fab0feae3e561561a82c1c7
Timestamp: 1580481571 Timestamp [UCT]: 2020-01-31 14:39:31 Age [y:d:h:m:s]: 05:034:04:21:56
Block: 55876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176272 RingCT/type: yes/0
Extra: 01730510b6d2844966fa32393c28e03d8d23ab35e43fab0feae3e561561a82c1c70211000000012264afe6000000000000000000

1 output(s) for total of 400.737921348000 dcy

stealth address amount amount idx
00: d40e6fdb5a212ce11f6545d404fcf98d44668b90cbe3b4bf73227a2e47fb8d63 400.737921348000 103072 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": 55886, "vin": [ { "gen": { "height": 55876 } } ], "vout": [ { "amount": 400737921348, "target": { "key": "d40e6fdb5a212ce11f6545d404fcf98d44668b90cbe3b4bf73227a2e47fb8d63" } } ], "extra": [ 1, 115, 5, 16, 182, 210, 132, 73, 102, 250, 50, 57, 60, 40, 224, 61, 141, 35, 171, 53, 228, 63, 171, 15, 234, 227, 229, 97, 86, 26, 130, 193, 199, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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