Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 144b2e956d1e78e918d9198ef7e816d7fc396ffb41b742e0ca4bea14bf7e8340

Tx prefix hash: dd4ee926e86459cb91e6b55a6e902d53c09224ce5d568e2c4f41deb2f27d9938
Tx public key: 5ca8a9fabd54f3ee7a98b0e77a7cfd1753bee370c8d5dfa6296382fc4a455cab
Timestamp: 1735474253 Timestamp [UCT]: 2024-12-29 12:10:53 Age [y:d:h:m:s]: 00:099:01:47:18
Block: 1185709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70602 RingCT/type: yes/0
Extra: 015ca8a9fabd54f3ee7a98b0e77a7cfd1753bee370c8d5dfa6296382fc4a455cab021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76713f311dfccb6d2a53aa7ced5416c594054981149fc48d2ad1bddbdfe96023 0.600000000000 1672184 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": 1185719, "vin": [ { "gen": { "height": 1185709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76713f311dfccb6d2a53aa7ced5416c594054981149fc48d2ad1bddbdfe96023" } } ], "extra": [ 1, 92, 168, 169, 250, 189, 84, 243, 238, 122, 152, 176, 231, 122, 124, 253, 23, 83, 190, 227, 112, 200, 213, 223, 166, 41, 99, 130, 252, 74, 69, 92, 171, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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