Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc73facc987c5cc5b94330bf4abdf264bf37f9c729dd37f4c91bbafbb2cc22d

Tx prefix hash: 7c2bc4c928a19c9656211a6e34890a6f5723731a0247d50cad6582d29ea907b9
Tx public key: 2e3a2a0941e5c8a4265a5419fcf673ac64b19c0efba80ca8ad061c257968e5c2
Timestamp: 1713938646 Timestamp [UCT]: 2024-04-24 06:04:06 Age [y:d:h:m:s]: 00:259:20:12:16
Block: 1007308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185981 RingCT/type: yes/0
Extra: 012e3a2a0941e5c8a4265a5419fcf673ac64b19c0efba80ca8ad061c257968e5c202110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 847a6bb8a73f5af1d4e4a315ff0de96fb1e3bdb5794d5ff12a3436aedd1806ba 0.600000000000 1468606 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": 1007318, "vin": [ { "gen": { "height": 1007308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "847a6bb8a73f5af1d4e4a315ff0de96fb1e3bdb5794d5ff12a3436aedd1806ba" } } ], "extra": [ 1, 46, 58, 42, 9, 65, 229, 200, 164, 38, 90, 84, 25, 252, 246, 115, 172, 100, 177, 156, 14, 251, 168, 12, 168, 173, 6, 28, 37, 121, 104, 229, 194, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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