Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acbf086c25bf6928acf870ffbe666ef6fd7ba105bd46de8950e15556b856d0fe

Tx prefix hash: b1d5df4198841db5ac0c0dff13f685245af20e76cff1e366528f1b259b3d7183
Tx public key: b6d1e9d39b58bdc20e0167fce3c56edd1d7949ca8b53757ce44135df4b1dc2a7
Timestamp: 1764055205 Timestamp [UCT]: 2025-11-25 07:20:05 Age [y:d:h:m:s]: 00:001:06:45:34
Block: 1419670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 912 RingCT/type: yes/0
Extra: 01b6d1e9d39b58bdc20e0167fce3c56edd1d7949ca8b53757ce44135df4b1dc2a702110000000517b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 414c947a44a5ebdb0f1ec1ac2afadf48ee8116181b58fe3250d0ea1545b179b0 0.600000000000 1908209 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": 1419680, "vin": [ { "gen": { "height": 1419670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "414c947a44a5ebdb0f1ec1ac2afadf48ee8116181b58fe3250d0ea1545b179b0" } } ], "extra": [ 1, 182, 209, 233, 211, 155, 88, 189, 194, 14, 1, 103, 252, 227, 197, 110, 221, 29, 121, 73, 202, 139, 83, 117, 124, 228, 65, 53, 223, 75, 29, 194, 167, 2, 17, 0, 0, 0, 5, 23, 177, 145, 50, 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