Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1abb89dac441d3fc625ebcbacdd6b59764ef401edb788213d6c5176a0429b416

Tx prefix hash: 4f9b12d1a1947fd836d82dcb3ccbb06129b20a8b0ff140f0c4dd9fb6ed450b34
Tx public key: 7ab31c265be54901c603f7699c5e09e16de7a1e21567d9f0a6536814acc237bb
Timestamp: 1717124135 Timestamp [UCT]: 2024-05-31 02:55:35 Age [y:d:h:m:s]: 00:350:11:44:09
Block: 1033715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250518 RingCT/type: yes/0
Extra: 017ab31c265be54901c603f7699c5e09e16de7a1e21567d9f0a6536814acc237bb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44fb2648f708fa227cd9b4f24c4688c2756b693882374ae3f908e41b4406b28 0.600000000000 1502186 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": 1033725, "vin": [ { "gen": { "height": 1033715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44fb2648f708fa227cd9b4f24c4688c2756b693882374ae3f908e41b4406b28" } } ], "extra": [ 1, 122, 179, 28, 38, 91, 229, 73, 1, 198, 3, 247, 105, 156, 94, 9, 225, 109, 231, 161, 226, 21, 103, 217, 240, 166, 83, 104, 20, 172, 194, 55, 187, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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