Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de7cdde1f8f54a405638f59642b0e3b0021774cf0dc868cd88deaf40bbc63f5

Tx prefix hash: 34441f975b067a007eaad5cbb9d1bc95097a49e278b88a1190e653d6d028b226
Tx public key: 6cb460c7954b599200d8d9bb486647f2b91abd6eacf89a036fb9c1ff934b7bab
Timestamp: 1704015352 Timestamp [UCT]: 2023-12-31 09:35:52 Age [y:d:h:m:s]: 01:161:22:54:06
Block: 925026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376917 RingCT/type: yes/0
Extra: 016cb460c7954b599200d8d9bb486647f2b91abd6eacf89a036fb9c1ff934b7bab0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 015615516584b47b50518b400025f300a87e96b8dcc3434accd0d83f2bbac93b 0.600000000000 1382786 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": 925036, "vin": [ { "gen": { "height": 925026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "015615516584b47b50518b400025f300a87e96b8dcc3434accd0d83f2bbac93b" } } ], "extra": [ 1, 108, 180, 96, 199, 149, 75, 89, 146, 0, 216, 217, 187, 72, 102, 71, 242, 185, 26, 189, 110, 172, 248, 154, 3, 111, 185, 193, 255, 147, 75, 123, 171, 2, 17, 0, 0, 0, 5, 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