Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9844db0134d773644c61e4136654403f895bb4e76f30fd13d88d02221b124dcd

Tx prefix hash: faa39a2e16201016857f9f7cd50fd79553f8b4bba57362a4835b39fe0999f9f8
Tx public key: 8d2e5b908a9b0a19e35401dd74104cb27dc4b19f6ee25e159530b78ab0c08304
Timestamp: 1677325221 Timestamp [UCT]: 2023-02-25 11:40:21 Age [y:d:h:m:s]: 01:273:07:03:26
Block: 704642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456229 RingCT/type: yes/0
Extra: 018d2e5b908a9b0a19e35401dd74104cb27dc4b19f6ee25e159530b78ab0c0830402110000000175e3f0e9000000000000000000

1 output(s) for total of 2.839412237000 dcy

stealth address amount amount idx
00: f840d7c6dcf9a6cb39b7c0b5a98e22e8a57c65664854c9acf645186ebba823dc 2.839412237000 1148313 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": 704652, "vin": [ { "gen": { "height": 704642 } } ], "vout": [ { "amount": 2839412237, "target": { "key": "f840d7c6dcf9a6cb39b7c0b5a98e22e8a57c65664854c9acf645186ebba823dc" } } ], "extra": [ 1, 141, 46, 91, 144, 138, 155, 10, 25, 227, 84, 1, 221, 116, 16, 76, 178, 125, 196, 177, 159, 110, 226, 94, 21, 149, 48, 183, 138, 176, 192, 131, 4, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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