Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fbf264523cf99785aaf443f28c63ba85fa2f596c41efce98d0433cc936e6ab4

Tx prefix hash: 50b72ba0cc7d6bc157cf5bcc4aaebc91fbbe484c0092ac9ef41201cdd2d2d9c5
Tx public key: 67716b95e4826ff79050daf73cdb884a1b316fe3e57b3581b8f8bdf4d1a67fc9
Timestamp: 1751541477 Timestamp [UCT]: 2025-07-03 11:17:57 Age [y:d:h:m:s]: 00:184:02:27:49
Block: 1317898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129889 RingCT/type: yes/0
Extra: 0167716b95e4826ff79050daf73cdb884a1b316fe3e57b3581b8f8bdf4d1a67fc902110000000b43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0a0b8a3b170a815336251ad6e4d889c66c9256cbf8d6014ba183dcb366b66b 0.600000000000 1805569 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": 1317908, "vin": [ { "gen": { "height": 1317898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0a0b8a3b170a815336251ad6e4d889c66c9256cbf8d6014ba183dcb366b66b" } } ], "extra": [ 1, 103, 113, 107, 149, 228, 130, 111, 247, 144, 80, 218, 247, 60, 219, 136, 74, 27, 49, 111, 227, 229, 123, 53, 129, 184, 248, 189, 244, 209, 166, 127, 201, 2, 17, 0, 0, 0, 11, 67, 132, 109, 102, 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