Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd123b1fb13abe5fe0021e244d0962859c0b49788df88e2c4a422e6ed54aa22f

Tx prefix hash: 2b29c36a3f9316b3fe75f1c3063422d6aed62c80397770d43765b5fa272d4586
Tx public key: 3a6dedb72dcf76d88aa9035f7c7b9523e5cfc12dbecc2310b8f7095b81c659de
Timestamp: 1736586480 Timestamp [UCT]: 2025-01-11 09:08:00 Age [y:d:h:m:s]: 00:345:16:31:15
Block: 1194931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244613 RingCT/type: yes/0
Extra: 013a6dedb72dcf76d88aa9035f7c7b9523e5cfc12dbecc2310b8f7095b81c659de021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8026decfee066a6b8772b382a75651740f42d39f6c97cc5bc67610a0f179786 0.600000000000 1681510 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": 1194941, "vin": [ { "gen": { "height": 1194931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8026decfee066a6b8772b382a75651740f42d39f6c97cc5bc67610a0f179786" } } ], "extra": [ 1, 58, 109, 237, 183, 45, 207, 118, 216, 138, 169, 3, 95, 124, 123, 149, 35, 229, 207, 193, 45, 190, 204, 35, 16, 184, 247, 9, 91, 129, 198, 89, 222, 2, 17, 0, 0, 0, 5, 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