Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111771970b3cbd2a4cb55c63ec1fce68055a1fed790b1b9735655395889f9a45

Tx prefix hash: 8146ac66839c5209518f9268632eb11c7c0b6cbf7c962b77bd365c4ed026930a
Tx public key: f7a1627d41065c8bf5305a68c0c1d7de6c25bcf84a9715049baf750f2b3da2f4
Timestamp: 1746429162 Timestamp [UCT]: 2025-05-05 07:12:42 Age [y:d:h:m:s]: 00:192:16:45:33
Block: 1276143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135434 RingCT/type: yes/0
Extra: 01f7a1627d41065c8bf5305a68c0c1d7de6c25bcf84a9715049baf750f2b3da2f40211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db1b1b504dd69cc3aa3c91121238b2346908d7c418cd55706f96db2fef3ed8aa 0.600000000000 1763466 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": 1276153, "vin": [ { "gen": { "height": 1276143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db1b1b504dd69cc3aa3c91121238b2346908d7c418cd55706f96db2fef3ed8aa" } } ], "extra": [ 1, 247, 161, 98, 125, 65, 6, 92, 139, 245, 48, 90, 104, 192, 193, 215, 222, 108, 37, 188, 248, 74, 151, 21, 4, 155, 175, 117, 15, 43, 61, 162, 244, 2, 17, 0, 0, 0, 1, 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