Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b599186ef3a8faf23816854977df11f34f5a56b653a206e7e216c1f1e59c3047

Tx prefix hash: d4ce803d2b3306e65173533ff44c643e9dd7eade955d21a0447a84b07b08be82
Tx public key: a474a0ca910ef9f9a57f6001dd97e2c1175e340aad81f5ba4aa922418facaff9
Timestamp: 1717702077 Timestamp [UCT]: 2024-06-06 19:27:57 Age [y:d:h:m:s]: 00:232:05:50:22
Block: 1038509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166162 RingCT/type: yes/0
Extra: 01a474a0ca910ef9f9a57f6001dd97e2c1175e340aad81f5ba4aa922418facaff902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8a984d447ba1c07c0b603437abf3d811d6be98111978b9ec2d878b915a9ac1 0.600000000000 1507070 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": 1038519, "vin": [ { "gen": { "height": 1038509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8a984d447ba1c07c0b603437abf3d811d6be98111978b9ec2d878b915a9ac1" } } ], "extra": [ 1, 164, 116, 160, 202, 145, 14, 249, 249, 165, 127, 96, 1, 221, 151, 226, 193, 23, 94, 52, 10, 173, 129, 245, 186, 74, 169, 34, 65, 143, 172, 175, 249, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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