Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d202cc532dc244f4f46cdffa0449ada3186b22786d74e789388057e719e3e8

Tx prefix hash: dd6a9d614be5cc1092736891458b75dbde6b623f1b8d485a8464f12d78cbe311
Tx public key: 30398ba8778c21865a0c1a6c57376295b2ace2a3e51e07c5b4be2abdada63e75
Timestamp: 1748810666 Timestamp [UCT]: 2025-06-01 20:44:26 Age [y:d:h:m:s]: 00:171:11:10:23
Block: 1295860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120240 RingCT/type: yes/0
Extra: 0130398ba8778c21865a0c1a6c57376295b2ace2a3e51e07c5b4be2abdada63e75021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e931a60ac8c26a5dc4aa3064772fad58d3abd318c7a86493457a9fb52b14db2 0.600000000000 1783367 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": 1295870, "vin": [ { "gen": { "height": 1295860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e931a60ac8c26a5dc4aa3064772fad58d3abd318c7a86493457a9fb52b14db2" } } ], "extra": [ 1, 48, 57, 139, 168, 119, 140, 33, 134, 90, 12, 26, 108, 87, 55, 98, 149, 178, 172, 226, 163, 229, 30, 7, 197, 180, 190, 42, 189, 173, 166, 62, 117, 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