Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa431426c327ea3aeb15d0d19ef301e0cf2215a4c4b93a5b7f6919392ffef9f4

Tx prefix hash: f16336fdf6aa2f3c36022c85413070d967dc7449f7f98a128270b95de800a7c7
Tx public key: 87718db2678579e56e0ed5de48b9d0e0a41f0e02debbfbb54ec1e80b807f4999
Timestamp: 1741022782 Timestamp [UCT]: 2025-03-03 17:26:22 Age [y:d:h:m:s]: 00:262:08:07:31
Block: 1231381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185235 RingCT/type: yes/0
Extra: 0187718db2678579e56e0ed5de48b9d0e0a41f0e02debbfbb54ec1e80b807f4999021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6feb7aa873e74013ea1ebf6ca89bdca31b58c0ed6309b86e30ab23ce2dd6f475 0.600000000000 1718288 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": 1231391, "vin": [ { "gen": { "height": 1231381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6feb7aa873e74013ea1ebf6ca89bdca31b58c0ed6309b86e30ab23ce2dd6f475" } } ], "extra": [ 1, 135, 113, 141, 178, 103, 133, 121, 229, 110, 14, 213, 222, 72, 185, 208, 224, 164, 31, 14, 2, 222, 187, 251, 181, 78, 193, 232, 11, 128, 127, 73, 153, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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