Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6660e507c8c87915d9ca4ce5ffb358a70d750469e31290fc234c32ffe5f4a0ec

Tx prefix hash: 381d76c8d0efc4b155626b5245c1f5fc0aa7122fb348e4033f175de6d8946656
Tx public key: 7b5e97e44eeaa0e810d79a4fd5745f60bf21ac091e4af2e2a03db7e06901fcc5
Timestamp: 1751189824 Timestamp [UCT]: 2025-06-29 09:37:04 Age [y:d:h:m:s]: 00:137:14:22:29
Block: 1315121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96457 RingCT/type: yes/0
Extra: 017b5e97e44eeaa0e810d79a4fd5745f60bf21ac091e4af2e2a03db7e06901fcc502110000000701491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f676694cb0d3682dde43bb34a5a6b590417bdf515a71c748ed91f55b909507c 0.600000000000 1802774 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": 1315131, "vin": [ { "gen": { "height": 1315121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f676694cb0d3682dde43bb34a5a6b590417bdf515a71c748ed91f55b909507c" } } ], "extra": [ 1, 123, 94, 151, 228, 78, 234, 160, 232, 16, 215, 154, 79, 213, 116, 95, 96, 191, 33, 172, 9, 30, 74, 242, 226, 160, 61, 183, 224, 105, 1, 252, 197, 2, 17, 0, 0, 0, 7, 1, 73, 31, 136, 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