Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e35c5773274ae42389381575b917ef00d4c3d419ed540224ce8c6b2107671e05

Tx prefix hash: 6b84398716eb949aed3645cea91dbda199cc502f17ba10dc4c58b2150bfb754c
Tx public key: d274e9a6d589f20793d913aaa38a6439aa2bd6f97da4c2cacbc1e5f24321460a
Timestamp: 1746131557 Timestamp [UCT]: 2025-05-01 20:32:37 Age [y:d:h:m:s]: 00:198:05:55:33
Block: 1273671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139408 RingCT/type: yes/0
Extra: 01d274e9a6d589f20793d913aaa38a6439aa2bd6f97da4c2cacbc1e5f24321460a0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82c03446f7a182f3801b3628a3927380a87b6b8b7dc8c4a4161f865439ea818b 0.600000000000 1760954 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": 1273681, "vin": [ { "gen": { "height": 1273671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82c03446f7a182f3801b3628a3927380a87b6b8b7dc8c4a4161f865439ea818b" } } ], "extra": [ 1, 210, 116, 233, 166, 213, 137, 242, 7, 147, 217, 19, 170, 163, 138, 100, 57, 170, 43, 214, 249, 125, 164, 194, 202, 203, 193, 229, 242, 67, 33, 70, 10, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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