Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f502cc97dd02cbe10b0252f9f4a5fdcbdfb34a542337cda1b14021a5ba4072

Tx prefix hash: 9f7c58498bc3f916e81ccaae5f9868313d3344189a9562d43cb7a4f620b3d8ef
Tx public key: f39f8843ea7b0ecaf1a4d27e01690ec4430b72b4d2b96df6b8a3509509ca3648
Timestamp: 1745731234 Timestamp [UCT]: 2025-04-27 05:20:34 Age [y:d:h:m:s]: 00:012:16:39:41
Block: 1270363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9080 RingCT/type: yes/0
Extra: 01f39f8843ea7b0ecaf1a4d27e01690ec4430b72b4d2b96df6b8a3509509ca36480211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7a5e7ed229a9f68b5e23c3e2e72aba04254dafa967a8132c4bb438d42a3708f 0.600000000000 1757606 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": 1270373, "vin": [ { "gen": { "height": 1270363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7a5e7ed229a9f68b5e23c3e2e72aba04254dafa967a8132c4bb438d42a3708f" } } ], "extra": [ 1, 243, 159, 136, 67, 234, 123, 14, 202, 241, 164, 210, 126, 1, 105, 14, 196, 67, 11, 114, 180, 210, 185, 109, 246, 184, 163, 80, 149, 9, 202, 54, 72, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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