Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db8bbf5e378febce865abb46a33c178cb1a67288978840c13fc7ebccdb9a02c

Tx prefix hash: 0e82bb9eca0531451bbfb2847503b216bde99b44bcb5058595f08615eefcca4c
Tx public key: d621d4fdbd9a0f2503dd2e89167cfe84cd1f161ee289423dcb9539b9a5830c92
Timestamp: 1749037017 Timestamp [UCT]: 2025-06-04 11:36:57 Age [y:d:h:m:s]: 00:209:00:31:35
Block: 1297752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147115 RingCT/type: yes/0
Extra: 01d621d4fdbd9a0f2503dd2e89167cfe84cd1f161ee289423dcb9539b9a5830c92021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a34191c8844098e004bf56f3f8d640d6a286bdea54ea247a12c0f86bf1b73d1b 0.600000000000 1785273 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": 1297762, "vin": [ { "gen": { "height": 1297752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a34191c8844098e004bf56f3f8d640d6a286bdea54ea247a12c0f86bf1b73d1b" } } ], "extra": [ 1, 214, 33, 212, 253, 189, 154, 15, 37, 3, 221, 46, 137, 22, 124, 254, 132, 205, 31, 22, 30, 226, 137, 66, 61, 203, 149, 57, 185, 165, 131, 12, 146, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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