Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38808c1a22d4ff0031849bfe40eba43bdb50bb7efdbd4533ed0aac4f32066b59

Tx prefix hash: b6866d87c4ee4d86edce8eafb2a1f4fdd7ebbcda36229b011ad4168278232637
Tx public key: 437e5145a09c551bfe4dcd6e6e9e17e7d1d112c9f11087c21d2ebc6f229f42bc
Timestamp: 1719681487 Timestamp [UCT]: 2024-06-29 17:18:07 Age [y:d:h:m:s]: 00:318:03:53:50
Block: 1054906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227381 RingCT/type: yes/0
Extra: 01437e5145a09c551bfe4dcd6e6e9e17e7d1d112c9f11087c21d2ebc6f229f42bc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5973fe92e8f09bfd5f8a9b5784de9986840e1389902f5f4cbf00af37a4e89587 0.600000000000 1525297 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": 1054916, "vin": [ { "gen": { "height": 1054906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5973fe92e8f09bfd5f8a9b5784de9986840e1389902f5f4cbf00af37a4e89587" } } ], "extra": [ 1, 67, 126, 81, 69, 160, 156, 85, 27, 254, 77, 205, 110, 110, 158, 23, 231, 209, 209, 18, 201, 241, 16, 135, 194, 29, 46, 188, 111, 34, 159, 66, 188, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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