Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f8be7cdfc5e58e3b12be05bf9dec1ef32eb377a50d49617826043181328a4c

Tx prefix hash: 78c38f6c2c4d95f6f737729cf441690d3b5b70e46d801ab59ee430b59f6b3bca
Tx public key: 22c329ebc796def8f2d238d5e636721dc81b375c26c47f8ad4933a89b6047116
Timestamp: 1730834227 Timestamp [UCT]: 2024-11-05 19:17:07 Age [y:d:h:m:s]: 00:018:12:02:34
Block: 1147288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13243 RingCT/type: yes/0
Extra: 0122c329ebc796def8f2d238d5e636721dc81b375c26c47f8ad4933a89b6047116021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff50042d6e47abfee2bad1dee5a73c64279a5f057d4dd488dded7bd591d282f 0.600000000000 1631983 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": 1147298, "vin": [ { "gen": { "height": 1147288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff50042d6e47abfee2bad1dee5a73c64279a5f057d4dd488dded7bd591d282f" } } ], "extra": [ 1, 34, 195, 41, 235, 199, 150, 222, 248, 242, 210, 56, 213, 230, 54, 114, 29, 200, 27, 55, 92, 38, 196, 127, 138, 212, 147, 58, 137, 182, 4, 113, 22, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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