Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd74bdb4a7437436c2169eb57c7748e141c63eeb1ac31b5789e7b46295368f49

Tx prefix hash: 5cecb0b0de16d3a79f291cbb3c9ace34cde289f53f42a5a702e91c9cad2dc0e5
Tx public key: 528f9016722132b31240f01cc1e6329d5758631a1dc6cabccae9479feedeb347
Timestamp: 1578522769 Timestamp [UCT]: 2020-01-08 22:32:49 Age [y:d:h:m:s]: 04:356:14:20:10
Block: 41658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144072 RingCT/type: yes/0
Extra: 01528f9016722132b31240f01cc1e6329d5758631a1dc6cabccae9479feedeb347021100000001b221b3d1000000000000000000

1 output(s) for total of 446.663032574000 dcy

stealth address amount amount idx
00: 3a99b3bc866f9711b59f6dd0d63aa8c868074cc2d7a4ad5d1cf514586f5321e5 446.663032574000 74406 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": 41668, "vin": [ { "gen": { "height": 41658 } } ], "vout": [ { "amount": 446663032574, "target": { "key": "3a99b3bc866f9711b59f6dd0d63aa8c868074cc2d7a4ad5d1cf514586f5321e5" } } ], "extra": [ 1, 82, 143, 144, 22, 114, 33, 50, 179, 18, 64, 240, 28, 193, 230, 50, 157, 87, 88, 99, 26, 29, 198, 202, 188, 202, 233, 71, 159, 238, 222, 179, 71, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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