Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683dcfedcb57f47b93e41812924c833ab2b9e1709f1ff5690647847dc244bc00

Tx prefix hash: ffa96363ae7adebe974e2b496cf11da40b0e6614ac7c30527a8ecd07c6a13f68
Tx public key: 5a4c6f48250357024efc28caa36145b64b046cf52c89278ba71535684b5b6b1b
Timestamp: 1716809289 Timestamp [UCT]: 2024-05-27 11:28:09 Age [y:d:h:m:s]: 00:308:00:38:38
Block: 1031120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220134 RingCT/type: yes/0
Extra: 015a4c6f48250357024efc28caa36145b64b046cf52c89278ba71535684b5b6b1b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9082bc187d3ee3ab9be510c68c8b9e44d6a86e4fd3aaa906d38bb71392d1d4d7 0.600000000000 1499489 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": 1031130, "vin": [ { "gen": { "height": 1031120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9082bc187d3ee3ab9be510c68c8b9e44d6a86e4fd3aaa906d38bb71392d1d4d7" } } ], "extra": [ 1, 90, 76, 111, 72, 37, 3, 87, 2, 78, 252, 40, 202, 163, 97, 69, 182, 75, 4, 108, 245, 44, 137, 39, 139, 167, 21, 53, 104, 75, 91, 107, 27, 2, 17, 0, 0, 0, 3, 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