Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f420ab5c957a3ab168b5985aa4bc436a289787f4a236706bdf5cc02dc89a0d

Tx prefix hash: 318ec1ab3356313858c364e076357d6d7f2a32816b9e6e9134d7e7901d9af962
Tx public key: 8d1acb65618fb5db66e0806078fb561be1f147c9e2593aa2baadf2abaf6437f7
Timestamp: 1721695678 Timestamp [UCT]: 2024-07-23 00:47:58 Age [y:d:h:m:s]: 00:124:16:39:51
Block: 1071602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89228 RingCT/type: yes/0
Extra: 018d1acb65618fb5db66e0806078fb561be1f147c9e2593aa2baadf2abaf6437f70211000000018f454fe7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a17cca06be24ac915ec3f8f4ad1de09b7b6a3161e5cf93e1700bcc0ad614d5f0 0.600000000000 1543893 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": 1071612, "vin": [ { "gen": { "height": 1071602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a17cca06be24ac915ec3f8f4ad1de09b7b6a3161e5cf93e1700bcc0ad614d5f0" } } ], "extra": [ 1, 141, 26, 203, 101, 97, 143, 181, 219, 102, 224, 128, 96, 120, 251, 86, 27, 225, 241, 71, 201, 226, 89, 58, 162, 186, 173, 242, 171, 175, 100, 55, 247, 2, 17, 0, 0, 0, 1, 143, 69, 79, 231, 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