Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed02f152c35eb972f51f0007090138f625ec05650d94eff5f42c78c4f7876a66

Tx prefix hash: 5321f77fb14bba7f903c7041d39110a2493527fb1a4ccf0b0cd8f01f00395f1f
Tx public key: 148f8b907ac4573158c9d8e396fea61c02817c3f8ab992e84986b6d5045f5880
Timestamp: 1750780545 Timestamp [UCT]: 2025-06-24 15:55:45 Age [y:d:h:m:s]: 00:148:16:05:44
Block: 1311911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104194 RingCT/type: yes/0
Extra: 01148f8b907ac4573158c9d8e396fea61c02817c3f8ab992e84986b6d5045f588002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27f4abf8ae2542cd50dda3de69b931017c0bc29214fdf19bae2a1e662aecfccd 0.600000000000 1799540 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": 1311921, "vin": [ { "gen": { "height": 1311911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27f4abf8ae2542cd50dda3de69b931017c0bc29214fdf19bae2a1e662aecfccd" } } ], "extra": [ 1, 20, 143, 139, 144, 122, 196, 87, 49, 88, 201, 216, 227, 150, 254, 166, 28, 2, 129, 124, 63, 138, 185, 146, 232, 73, 134, 182, 213, 4, 95, 88, 128, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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