Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87781ff630833bc6cdab838301f36485e1427e88e6ba9f7cec8100d1e1437fd9

Tx prefix hash: 15a0b24e9f15001048d9922d23613267480157e1e36dd809cf1bb5da04061050
Tx public key: 926651e3e6e02ce24b2bd7920ebcdd835290aa6db8005c8d0142b671d4adae0c
Timestamp: 1713946159 Timestamp [UCT]: 2024-04-24 08:09:19 Age [y:d:h:m:s]: 00:352:18:37:47
Block: 1007374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252186 RingCT/type: yes/0
Extra: 01926651e3e6e02ce24b2bd7920ebcdd835290aa6db8005c8d0142b671d4adae0c02110000001352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef681a6d04c0867fb9f7aad601f5fcaae4d5e0f58a847246a51d5094490329a6 0.600000000000 1468694 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": 1007384, "vin": [ { "gen": { "height": 1007374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef681a6d04c0867fb9f7aad601f5fcaae4d5e0f58a847246a51d5094490329a6" } } ], "extra": [ 1, 146, 102, 81, 227, 230, 224, 44, 226, 75, 43, 215, 146, 14, 188, 221, 131, 82, 144, 170, 109, 184, 0, 92, 141, 1, 66, 182, 113, 212, 173, 174, 12, 2, 17, 0, 0, 0, 19, 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