Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d39e7e114bcee5be256ff40aac4059586b7a9427b599e352c25ce733f60c1272

Tx prefix hash: da47f26b76b895bdc42eb1338bff40bc2d35b8513653019332c38f269b1d64b6
Tx public key: dfea47409d3449a2dfef3173c6e287fd97c71c84c261c321ad2a6e762a23fe54
Timestamp: 1705740970 Timestamp [UCT]: 2024-01-20 08:56:10 Age [y:d:h:m:s]: 01:095:01:27:40
Block: 939304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329068 RingCT/type: yes/0
Extra: 01dfea47409d3449a2dfef3173c6e287fd97c71c84c261c321ad2a6e762a23fe540211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba614253d78530221b8f72f10318df9837a83a89d5bc2e070ae331f629dac4c7 0.600000000000 1397396 of 15

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": 939314, "vin": [ { "gen": { "height": 939304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba614253d78530221b8f72f10318df9837a83a89d5bc2e070ae331f629dac4c7" } } ], "extra": [ 1, 223, 234, 71, 64, 157, 52, 73, 162, 223, 239, 49, 115, 198, 226, 135, 253, 151, 199, 28, 132, 194, 97, 195, 33, 173, 42, 110, 118, 42, 35, 254, 84, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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