Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b91235f2c9830e1fd8afdd1c38f2ee83561dfe7bf9f00a1874aafe3ff7418f3

Tx prefix hash: 471755d7a798f662a626dc86b568de26cf9e8fcf5eecc8d99427d57de993c5a9
Tx public key: cdfeead547da5d5e32e2523789d7bb3753be6bb467c0a8a245a4f7f45ad57162
Timestamp: 1718781929 Timestamp [UCT]: 2024-06-19 07:25:29 Age [y:d:h:m:s]: 00:329:00:56:31
Block: 1047461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235159 RingCT/type: yes/0
Extra: 01cdfeead547da5d5e32e2523789d7bb3753be6bb467c0a8a245a4f7f45ad571620211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be095e56f6f2951266004b8352e7102c9050eecdd1b255be89babd33d49e73f 0.600000000000 1517292 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": 1047471, "vin": [ { "gen": { "height": 1047461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be095e56f6f2951266004b8352e7102c9050eecdd1b255be89babd33d49e73f" } } ], "extra": [ 1, 205, 254, 234, 213, 71, 218, 93, 94, 50, 226, 82, 55, 137, 215, 187, 55, 83, 190, 107, 180, 103, 192, 168, 162, 69, 164, 247, 244, 90, 213, 113, 98, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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