Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6015c9113b03007b6b4188adc53fabfb4c15472f4b2ae8974d195f5f2bf24ebe

Tx prefix hash: 3494a420f75b05fc3b5efdeb763bc9ef39d02011141810e7a5d981d08d9a7065
Tx public key: 4649fa86f03c8bd6c7ba444164893b765d226a8785dfe0ca3d5cd9d4296c36f9
Timestamp: 1673097862 Timestamp [UCT]: 2023-01-07 13:24:22 Age [y:d:h:m:s]: 02:100:22:14:24
Block: 669573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593822 RingCT/type: yes/0
Extra: 014649fa86f03c8bd6c7ba444164893b765d226a8785dfe0ca3d5cd9d4296c36f902110000000152542ceb000000000000000000

1 output(s) for total of 3.710450617000 dcy

stealth address amount amount idx
00: 7672167aaab998c95fa3b9d4475c523d8f9ecbcd9c1c91e6be69ef61c56921d0 3.710450617000 1110916 of 0

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": 669583, "vin": [ { "gen": { "height": 669573 } } ], "vout": [ { "amount": 3710450617, "target": { "key": "7672167aaab998c95fa3b9d4475c523d8f9ecbcd9c1c91e6be69ef61c56921d0" } } ], "extra": [ 1, 70, 73, 250, 134, 240, 60, 139, 214, 199, 186, 68, 65, 100, 137, 59, 118, 93, 34, 106, 135, 133, 223, 224, 202, 61, 92, 217, 212, 41, 108, 54, 249, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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