Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 740c053187fc3f18f16b904d001170254cac2eee6a2ec9a04671163891144931

Tx prefix hash: a92280fca4a471ea552908138c4240e74d4af2763fca9cc93543f3a1e023b3a1
Tx public key: b5f6ff7e5de29e7caeda88125e3343214759f91bb0002e8af8829ed9a4fba2bc
Timestamp: 1584898337 Timestamp [UCT]: 2020-03-22 17:32:17 Age [y:d:h:m:s]: 04:283:02:27:29
Block: 86510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099427 RingCT/type: yes/0
Extra: 01b5f6ff7e5de29e7caeda88125e3343214759f91bb0002e8af8829ed9a4fba2bc021100000009d81c26c0000000000000000000

1 output(s) for total of 317.217573250000 dcy

stealth address amount amount idx
00: df91aee74e5bbb8e619815e47e928bfe12ae82e3b5cbecd642abd3d15ee52876 317.217573250000 156102 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": 86520, "vin": [ { "gen": { "height": 86510 } } ], "vout": [ { "amount": 317217573250, "target": { "key": "df91aee74e5bbb8e619815e47e928bfe12ae82e3b5cbecd642abd3d15ee52876" } } ], "extra": [ 1, 181, 246, 255, 126, 93, 226, 158, 124, 174, 218, 136, 18, 94, 51, 67, 33, 71, 89, 249, 27, 176, 0, 46, 138, 248, 130, 158, 217, 164, 251, 162, 188, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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