Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a6b70a08cc5847ec0e74c9fe0177d1922cd811ebddd9c2373c5fd9ef4ce97cb

Tx prefix hash: 8bc33271217bc4caa68572b63dff4ee3e8fa9fb024d025e3f95628d52983b039
Tx public key: b9cb93b4fef2f205f09cd147d4928f488719e51abc98b642260460d587b7ee98
Timestamp: 1718892874 Timestamp [UCT]: 2024-06-20 14:14:34 Age [y:d:h:m:s]: 00:335:00:32:57
Block: 1048378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239439 RingCT/type: yes/0
Extra: 01b9cb93b4fef2f205f09cd147d4928f488719e51abc98b642260460d587b7ee980211000000030bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536113d33338217af5d0dba7c22fe2ff33f88f7fb3b4adf158b2f52d4f0b29bf 0.600000000000 1518451 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": 1048388, "vin": [ { "gen": { "height": 1048378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536113d33338217af5d0dba7c22fe2ff33f88f7fb3b4adf158b2f52d4f0b29bf" } } ], "extra": [ 1, 185, 203, 147, 180, 254, 242, 242, 5, 240, 156, 209, 71, 212, 146, 143, 72, 135, 25, 229, 26, 188, 152, 182, 66, 38, 4, 96, 213, 135, 183, 238, 152, 2, 17, 0, 0, 0, 3, 11, 186, 22, 215, 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