Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51fb873b16fba06baacf6444eafc410ee3bf29db21ff3b2e3e167002a2b485c7

Tx prefix hash: df4a076084bf8ba2e2063b7ea8713c38753939010f69dcc0871f53ac1373f717
Tx public key: 8d4069862d75df3a62fb5b16c5a941fc47ccd841f52881037cacecf336e81224
Timestamp: 1705702280 Timestamp [UCT]: 2024-01-19 22:11:20 Age [y:d:h:m:s]: 01:296:21:26:55
Block: 938988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471024 RingCT/type: yes/0
Extra: 018d4069862d75df3a62fb5b16c5a941fc47ccd841f52881037cacecf336e812240211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d66f1ee45055cdf07eaf54b0dd9d20d3eb3e245ca91027d589c9378103dd5a74 0.600000000000 1397072 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": 938998, "vin": [ { "gen": { "height": 938988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d66f1ee45055cdf07eaf54b0dd9d20d3eb3e245ca91027d589c9378103dd5a74" } } ], "extra": [ 1, 141, 64, 105, 134, 45, 117, 223, 58, 98, 251, 91, 22, 197, 169, 65, 252, 71, 204, 216, 65, 245, 40, 129, 3, 124, 172, 236, 243, 54, 232, 18, 36, 2, 17, 0, 0, 0, 4, 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