Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a0d44f36dfb2aaefa242b9f6733f252a0890dd189acfa90ff3e7bc5b75d821

Tx prefix hash: 26fef6cada05b06f8ee748c773d424dccb6001c72147cad21dbabf66b695d149
Tx public key: 93c132afa5b147aa7109a513c4d6279a6acd0e35b6947380561233bb48d56c6d
Timestamp: 1717402722 Timestamp [UCT]: 2024-06-03 08:18:42 Age [y:d:h:m:s]: 00:178:16:05:21
Block: 1036034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127868 RingCT/type: yes/0
Extra: 0193c132afa5b147aa7109a513c4d6279a6acd0e35b6947380561233bb48d56c6d021100000004162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 876520e1d3a52dc308327efca3d4ed0968d22d7ee0d1aaf0c8f6e6a7d3c6e589 0.600000000000 1504559 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": 1036044, "vin": [ { "gen": { "height": 1036034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "876520e1d3a52dc308327efca3d4ed0968d22d7ee0d1aaf0c8f6e6a7d3c6e589" } } ], "extra": [ 1, 147, 193, 50, 175, 165, 177, 71, 170, 113, 9, 165, 19, 196, 214, 39, 154, 106, 205, 14, 53, 182, 148, 115, 128, 86, 18, 51, 187, 72, 213, 108, 109, 2, 17, 0, 0, 0, 4, 22, 38, 19, 170, 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