Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898a9d312f04eb32cb97d6b30d44852655f218f24b65051625414f5ec227c8f1

Tx prefix hash: 9e5c1f48a61a32354a4f4f78f03cb150b5dad43f14e5e2f146945e462ae319f6
Tx public key: 2671039069b5f9cfee41c5ae59b7bbef23c0461733b07125abe2ef7a0f93d729
Timestamp: 1723032718 Timestamp [UCT]: 2024-08-07 12:11:58 Age [y:d:h:m:s]: 01:093:19:17:17
Block: 1082696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325519 RingCT/type: yes/0
Extra: 012671039069b5f9cfee41c5ae59b7bbef23c0461733b07125abe2ef7a0f93d729021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 440935fec249b39bf429d8be8d85e261cc0276b0b4fca6300a1d5eb04726b0a5 0.600000000000 1556527 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": 1082706, "vin": [ { "gen": { "height": 1082696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "440935fec249b39bf429d8be8d85e261cc0276b0b4fca6300a1d5eb04726b0a5" } } ], "extra": [ 1, 38, 113, 3, 144, 105, 181, 249, 207, 238, 65, 197, 174, 89, 183, 187, 239, 35, 192, 70, 23, 51, 176, 113, 37, 171, 226, 239, 122, 15, 147, 215, 41, 2, 17, 0, 0, 0, 8, 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