Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8acd1143f636d690f037745c45dbc4d62138460b50224ac156222851a57fbf01

Tx prefix hash: dd91ac2d93e1a73a419a77110869f9a4a73a6b5694d2fa959895c3d515d5a27a
Tx public key: 22e44b64d6016c270766fd2a4b42109eb5de6cb561f84da8719043a1cb38a0c4
Timestamp: 1716978856 Timestamp [UCT]: 2024-05-29 10:34:16 Age [y:d:h:m:s]: 00:312:07:14:26
Block: 1032515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223187 RingCT/type: yes/0
Extra: 0122e44b64d6016c270766fd2a4b42109eb5de6cb561f84da8719043a1cb38a0c402110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1249ac43cb37f3dea90e7c0551b8f26a87c2cea85a9c2f07471e8499041b8475 0.600000000000 1500968 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": 1032525, "vin": [ { "gen": { "height": 1032515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1249ac43cb37f3dea90e7c0551b8f26a87c2cea85a9c2f07471e8499041b8475" } } ], "extra": [ 1, 34, 228, 75, 100, 214, 1, 108, 39, 7, 102, 253, 42, 75, 66, 16, 158, 181, 222, 108, 181, 97, 248, 77, 168, 113, 144, 67, 161, 203, 56, 160, 196, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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