Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ee68b5dea3fd21640c4563ab6bce1bf83fb52d058dbbbe2a66ead92af1e6ce

Tx prefix hash: 8b44c43b733637c844b32f4e8e0949f2a8afc56b7169e58c61549b777399f11e
Tx public key: 1d159415125dabc08d0573ce6a2b3231b2f094e86e073e5213af0d3e83b0a365
Timestamp: 1718775923 Timestamp [UCT]: 2024-06-19 05:45:23 Age [y:d:h:m:s]: 00:282:13:22:04
Block: 1047411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201907 RingCT/type: yes/0
Extra: 011d159415125dabc08d0573ce6a2b3231b2f094e86e073e5213af0d3e83b0a36502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96816229479b1604f9363ed2b7f20a1d83ac287b4eded454a1e48faf2524bbe0 0.600000000000 1517232 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": 1047421, "vin": [ { "gen": { "height": 1047411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96816229479b1604f9363ed2b7f20a1d83ac287b4eded454a1e48faf2524bbe0" } } ], "extra": [ 1, 29, 21, 148, 21, 18, 93, 171, 192, 141, 5, 115, 206, 106, 43, 50, 49, 178, 240, 148, 232, 110, 7, 62, 82, 19, 175, 13, 62, 131, 176, 163, 101, 2, 17, 0, 0, 0, 1, 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