Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2549a73d6be7fcd71c8bc67a8f2c1d647d614052cb7f94e6dac05e80b5f51f3

Tx prefix hash: ee1649eaba207d1b86c74478b0a3efe6c92815054877228c5149e80cf72002d1
Tx public key: 8f026e9d65fa5835dc873de0676e2c8b75cecca5e377f8538d67bda23659226a
Timestamp: 1711080820 Timestamp [UCT]: 2024-03-22 04:13:40 Age [y:d:h:m:s]: 01:055:01:35:52
Block: 983630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300337 RingCT/type: yes/0
Extra: 018f026e9d65fa5835dc873de0676e2c8b75cecca5e377f8538d67bda23659226a02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a5bb028776742b97bab4abf84612d96e2647249c8251f93590874b76eab01f 0.600000000000 1443771 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": 983640, "vin": [ { "gen": { "height": 983630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a5bb028776742b97bab4abf84612d96e2647249c8251f93590874b76eab01f" } } ], "extra": [ 1, 143, 2, 110, 157, 101, 250, 88, 53, 220, 135, 61, 224, 103, 110, 44, 139, 117, 206, 204, 165, 227, 119, 248, 83, 141, 103, 189, 162, 54, 89, 34, 106, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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