Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5b8f2cbb418d7dac7267214c4233916f6801cca492ae4e228ea3366895a1f0

Tx prefix hash: e454922f85590c7efe3cde894cf28755a5366f74e8ba8ad996dc94024198ebd6
Tx public key: 1be5be1d3926eb3280d17dbad6d7d148a42275c8aa9f510865423e61c25c711a
Timestamp: 1752284977 Timestamp [UCT]: 2025-07-12 01:49:37 Age [y:d:h:m:s]: 00:181:06:41:13
Block: 1323597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128331 RingCT/type: yes/0
Extra: 011be5be1d3926eb3280d17dbad6d7d148a42275c8aa9f510865423e61c25c711a021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60462d4f0654dd2c7ba9143fefc98aba62b37018fdc51b832d021004fe690a4 0.600000000000 1811336 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": 1323607, "vin": [ { "gen": { "height": 1323597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60462d4f0654dd2c7ba9143fefc98aba62b37018fdc51b832d021004fe690a4" } } ], "extra": [ 1, 27, 229, 190, 29, 57, 38, 235, 50, 128, 209, 125, 186, 214, 215, 209, 72, 164, 34, 117, 200, 170, 159, 81, 8, 101, 66, 62, 97, 194, 92, 113, 26, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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