Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f416478ae5f11bb734740619495fc9b3be8f7cec366f8e552ba849fc8a35e85

Tx prefix hash: 121e81aa080d8355bf7d5ce78714430f1076dfb04055791b2d23ff598d36fe6e
Tx public key: 8198a1d9c689c9efcc2710a060c16537f9fed55a3323e1706a2b0ea6aa8e82d6
Timestamp: 1712253451 Timestamp [UCT]: 2024-04-04 17:57:31 Age [y:d:h:m:s]: 01:040:17:51:00
Block: 993303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290130 RingCT/type: yes/0
Extra: 018198a1d9c689c9efcc2710a060c16537f9fed55a3323e1706a2b0ea6aa8e82d60211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7720634baf8c74eca2b1963f06f6ca63ed9b4834215404a6d94be6e1b3c14c6 0.600000000000 1453689 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": 993313, "vin": [ { "gen": { "height": 993303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7720634baf8c74eca2b1963f06f6ca63ed9b4834215404a6d94be6e1b3c14c6" } } ], "extra": [ 1, 129, 152, 161, 217, 198, 137, 201, 239, 204, 39, 16, 160, 96, 193, 101, 55, 249, 254, 213, 90, 51, 35, 225, 112, 106, 43, 14, 166, 170, 142, 130, 214, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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