Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63bab3238acd230cd08a1a094b43e6e208147f9ae65d4ae37d4da9accd64a1ab

Tx prefix hash: 7e01f41f7e16e0978593b2f3f34b2d766bef241e3f962ebaadd4f13ded7b9ff3
Tx public key: dff7665e511e287c02e9c75bcc6ce02da98bb102ff24b9c61719572a5c474200
Timestamp: 1716087407 Timestamp [UCT]: 2024-05-19 02:56:47 Age [y:d:h:m:s]: 00:307:20:03:43
Block: 1025118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220033 RingCT/type: yes/0
Extra: 01dff7665e511e287c02e9c75bcc6ce02da98bb102ff24b9c61719572a5c4742000211000000030011055b000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 5334b23ea702c68c7c3a0000cc2489e137fd1744b589af9468e4cd61b3c958ae 0.615590000000 1491385 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": 1025128, "vin": [ { "gen": { "height": 1025118 } } ], "vout": [ { "amount": 615590000, "target": { "key": "5334b23ea702c68c7c3a0000cc2489e137fd1744b589af9468e4cd61b3c958ae" } } ], "extra": [ 1, 223, 247, 102, 94, 81, 30, 40, 124, 2, 233, 199, 91, 204, 108, 224, 45, 169, 139, 177, 2, 255, 36, 185, 198, 23, 25, 87, 42, 92, 71, 66, 0, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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