Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec470bdfbef5bae0ff5cd61c1427e7f0b6d4595fdf22406420cba63ba08e6ee

Tx prefix hash: 903d1579373fc80c89f1260b45ffc62f65cdaae89b58d640dd1289394db89517
Tx public key: d1fcce9dbb45aae5b58d79a916e83ee478db70074f982724fe6e57a652460ead
Timestamp: 1574660750 Timestamp [UCT]: 2019-11-25 05:45:50 Age [y:d:h:m:s]: 05:002:17:10:38
Block: 16950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144765 RingCT/type: yes/0
Extra: 01d1fcce9dbb45aae5b58d79a916e83ee478db70074f982724fe6e57a652460ead021100000001f95225a5000000000000000000

1 output(s) for total of 539.310027166000 dcy

stealth address amount amount idx
00: ce9c6e3a0d3b24514739acc865239397e0d60180f14a8dd9d75d4d2e6a04178d 539.310027166000 24158 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": 16960, "vin": [ { "gen": { "height": 16950 } } ], "vout": [ { "amount": 539310027166, "target": { "key": "ce9c6e3a0d3b24514739acc865239397e0d60180f14a8dd9d75d4d2e6a04178d" } } ], "extra": [ 1, 209, 252, 206, 157, 187, 69, 170, 229, 181, 141, 121, 169, 22, 232, 62, 228, 120, 219, 112, 7, 79, 152, 39, 36, 254, 110, 87, 166, 82, 70, 14, 173, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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