Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e8c6d104dc496e177fab8cb24b393f48e0aee7897b4bc79368dbfa6357f94f

Tx prefix hash: c112bafb46b84a597073c61d3765cbbf964715c778f3bc3192684feb06ae2387
Tx public key: 3a202d4f2b3cdd129b2c77d8e88fe75d67208e5e729e5b1ded68014f7aa55985
Timestamp: 1725195617 Timestamp [UCT]: 2024-09-01 13:00:17 Age [y:d:h:m:s]: 00:052:06:19:21
Block: 1100633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37401 RingCT/type: yes/0
Extra: 013a202d4f2b3cdd129b2c77d8e88fe75d67208e5e729e5b1ded68014f7aa55985021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98ab90aa0ab721facdd6c5329121f8248bf64cc36d76e246f3332d7d8c6e7adb 0.600000000000 1576612 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": 1100643, "vin": [ { "gen": { "height": 1100633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ab90aa0ab721facdd6c5329121f8248bf64cc36d76e246f3332d7d8c6e7adb" } } ], "extra": [ 1, 58, 32, 45, 79, 43, 60, 221, 18, 155, 44, 119, 216, 232, 143, 231, 93, 103, 32, 142, 94, 114, 158, 91, 29, 237, 104, 1, 79, 122, 165, 89, 133, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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