Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49b93d0e80da4b3a92f9275b9870f8eb736ead88b16f4718b60b57659508c28

Tx prefix hash: a8a7f89b417555a3f05c797280910d0fd2eb2f7dee864f23f0d5199a83e0d8f9
Tx public key: f5304c65d10fd92f743d643bbf017a349a4efe6266276621d2c245677143c604
Timestamp: 1718677501 Timestamp [UCT]: 2024-06-18 02:25:01 Age [y:d:h:m:s]: 00:218:15:52:42
Block: 1046594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156433 RingCT/type: yes/0
Extra: 01f5304c65d10fd92f743d643bbf017a349a4efe6266276621d2c245677143c6040211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32d0949c7017df007d18c1b53633d08079e12598bbd6313779b5659fa047ed1e 0.600000000000 1516409 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": 1046604, "vin": [ { "gen": { "height": 1046594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32d0949c7017df007d18c1b53633d08079e12598bbd6313779b5659fa047ed1e" } } ], "extra": [ 1, 245, 48, 76, 101, 209, 15, 217, 47, 116, 61, 100, 59, 191, 1, 122, 52, 154, 78, 254, 98, 102, 39, 102, 33, 210, 194, 69, 103, 113, 67, 198, 4, 2, 17, 0, 0, 0, 5, 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