Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5fbb09111b3098cf5cbe4643b665b4fae747f283f3ec81aab8a8f4f558416c

Tx prefix hash: bde42973ef1dba7dfc0df1b589669335472ca740a3bd022013ec661adaa3ebd2
Tx public key: cb914f637a2e440be141257de8db4db34ef93f3895fe5e476bd8a89c1b2ec8c9
Timestamp: 1737956836 Timestamp [UCT]: 2025-01-27 05:47:16 Age [y:d:h:m:s]: 00:144:05:17:58
Block: 1206032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102972 RingCT/type: yes/0
Extra: 01cb914f637a2e440be141257de8db4db34ef93f3895fe5e476bd8a89c1b2ec8c90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ed5b4bd18fa309df0b292046af3c77c09316876b021b60e0d033e80ddb8c040 0.600000000000 1692733 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": 1206042, "vin": [ { "gen": { "height": 1206032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ed5b4bd18fa309df0b292046af3c77c09316876b021b60e0d033e80ddb8c040" } } ], "extra": [ 1, 203, 145, 79, 99, 122, 46, 68, 11, 225, 65, 37, 125, 232, 219, 77, 179, 78, 249, 63, 56, 149, 254, 94, 71, 107, 216, 168, 156, 27, 46, 200, 201, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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