Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db491543e67a2abd897c8f970a50573c4a18140784e985e58ed84d307d781db8

Tx prefix hash: b08f674b0147bf935b8b30ceba9446827ef04e52470dd6682d4b8068bcda282c
Tx public key: 2d83d8163f14d983eb024788b0c70f4c03f81a058bda1a314d328c48ae5f8784
Timestamp: 1762562377 Timestamp [UCT]: 2025-11-08 00:39:37 Age [y:d:h:m:s]: 00:045:11:32:43
Block: 1407294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32556 RingCT/type: yes/0
Extra: 012d83d8163f14d983eb024788b0c70f4c03f81a058bda1a314d328c48ae5f8784021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9385631d9078f3f996a2955cc4b33a57fde57a333f2980491f9548fe1edea343 0.600000000000 1895713 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": 1407304, "vin": [ { "gen": { "height": 1407294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9385631d9078f3f996a2955cc4b33a57fde57a333f2980491f9548fe1edea343" } } ], "extra": [ 1, 45, 131, 216, 22, 63, 20, 217, 131, 235, 2, 71, 136, 176, 199, 15, 76, 3, 248, 26, 5, 139, 218, 26, 49, 77, 50, 140, 72, 174, 95, 135, 132, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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